Great work! I confirmed that I could render the min / max lines and receive different data visualizations with different transformation.

I did a pre-review per your request. I found an ESLINT error and made some code recommendations / nitpicks (feel free to ignore if you don't agree). We might want to break up any new UX requirements into separate tickets if needed. Fixing the accessibility issues found by Axe might not be practical and will need to addressed in the Gen3.2 port.

UX Suggestions:

• Add chart icon to initial screen per design
• Style chart title to be bold
• Format labels for dropdowns to match design
• Implementation missing text version, and text version / Histogram button controls
• Add label for transformation dropdown and place below Cancel / Submit buttons
• Use controlled react components to store state of user selections - I'm seeing a bug where the user inputs disappear after inputting them and changing the transformation type. However, I think the lines associated with the min and max values remain after the chart redrawing.

Notes on Input UX & Error Messaging:

• Currently users can enter non-numeric inputs into the input fields (which then are deleted when leaving focus). Consider adding an error message to let user know only numeric inputs are allowed after user enters an invalid input type.
• Consider adding error messaging for numeric inputs that make the chart render oddly or prevent invalid inputs. For example, if the user adds mins and maximums of -123456789101112131415 and 123456789101112131415 the chart's labels overlap.
• Consider adding error messaging if the min exceeds the max and vice-versa.
• Consider adding error messaging if min exactly equals max

Accessibility Issues:

• In Transformation dropdown: Missing labels for form elements
• In Transformation dropdown: Ensure elements with ARIA roles have all required ARIA attributes

DESIGN

IMPLEMENTATION

FOUND ACCESSIBILITY ISSUES